Fix initialization of Taskwarrior on Dockerfile - #4159
Merged
Conversation
Add the 'default.theme' to the test Docker file and create empty '.taskrc'. Those two files are the minimum requirements for Taskwarrior to run
felixschurk
approved these changes
Jul 29, 2026
felixschurk
left a comment
felixschurk
left a comment
Collaborator
There was a problem hiding this comment.
Looks good and reasonable!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the 'default.theme' to the test Docker file and create empty '.taskrc'.
Those two files are the minimum requirements for Taskwarrior to run.
This fixes the e2e tests for the [task-timewarrior-hook] which require an image with running Taskwarrior and Timewarrior.
Without the two files, Taskwarrior exits with error message,
causing the e2e tests to fail.